Processing blockchain data based on smart contract operations executed in a trusted execution environment

ABSTRACT

Disclosed herein are methods, systems, and apparatus, including computer programs encoded on computer storage media, for processing blockchain data under a trusted execution environment (TEE). One of the methods includes receiving, by a blockchain node, a request to execute one or more software instructions in a TEE executing on the blockchain node; determining, by a virtual machine in the TEE, data associated with one or more blockchain accounts to execute the one or more software instructions based on the request; traversing, by the virtual machine, a global state of a blockchain stored in the TEE to locate the data; and executing, by the virtual machine, the one or more software instructions based on the data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit of priorityof U.S. patent application Ser. No. 16/670,646, filed Oct. 31, 2019,which is a continuation of PCT Application No. PCT/CN2019/081180, filedon Apr. 3, 2019, which is hereby incorporated by reference in itsentirety.

TECHNICAL FIELD

This specification relates to processing blockchain data under a trustedexecution environment.

BACKGROUND

Distributed ledger systems (DLSs), which can also be referred to asconsensus networks, and/or blockchain networks, enable participatingentities to securely, and immutably store data. DLSs are commonlyreferred to as blockchain networks without referencing any particularuser case. Examples of types of blockchain networks can include publicblockchain networks, private blockchain networks, and consortiumblockchain networks. A consortium blockchain network is provided for aselect group of entities, which control the consensus process, andincludes an access control layer.

Smart contracts are programs that execute on blockchains. A smartcontract contains a set of pre-defined rules under which the parties tothat smart contract agree to interact with each other. Smart contractscan be executed by distributed computing platforms such as Ethereum. Forexample, the Ethereum virtual machine (EVM) provides the runtimeenvironment for smart contracts in Ethereum. An Ethereum blockchain canbe viewed as a transaction-based state machine. Ethereum can have aglobal shared-state referred to as a world state. The world statecomprises a mapping between Ethereum account addresses and accountstates. The mapping is stored in a data structure known as a MerklePatricia tree (MPT).

Although the Ethereum account states are often encrypted to protectaccount privacy, the encryption key used is the same for all accounts.As such, the data structure of the MPT can be preserved, so that theMerkle root can be calculated in the same way by all blockchain nodesfor Merkle proof or state updates. However, by using the same encryptionkey among all accounts, the data structure of the world state cannot behidden, and privacy information associated with account relationshipsand behaviors may be analyzed by attackers.

Accordingly, it would be desirable to retrieve and update the accountvalues of a blockchain in a trusted execution environment and store thecorresponding MPT in cyphertext to hide its data structure.

SUMMARY

This specification describes technologies for processing blockchain databased on smart contract operations executed in a trusted executionenvironment (TEE). These technologies generally involve receiving arequest to execute one or more software instructions in a TEE executingon the blockchain node; determining data associated with one or moreblockchain accounts to execute the one or more software instructionsbased on the request; traversing a global state of a blockchain storedin the TEE to locate the data; and executing the one or more softwareinstructions based on the data.

This specification also provides one or more non-transitorycomputer-readable storage media coupled to one or more processors andhaving instructions stored thereon which, when executed by the one ormore processors, cause the one or more processors to perform operationsin accordance with embodiments of the methods provided herein.

This specification further provides a system for implementing themethods provided herein. The system includes one or more processors, anda computer-readable storage medium coupled to the one or more processorshaving instructions stored thereon which, when executed by the one ormore processors, cause the one or more processors to perform operationsin accordance with embodiments of the methods provided herein.

It is appreciated that methods in accordance with this specification mayinclude any combination of the aspects and features described herein.That is, methods in accordance with this specification are not limitedto the combinations of aspects and features specifically describedherein, but also include any combination of the aspects and featuresprovided.

The details of one or more embodiments of this specification are setforth in the accompanying drawings and the description below. Otherfeatures and advantages of this specification will be apparent from thedescription and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of an environment that canbe used to execute embodiments of this specification.

FIG. 2 is a diagram illustrating an example of an architecture inaccordance with embodiments of this specification.

FIG. 3 is a diagram illustrating an example of a structure of a TEE incommunication with a database outside of the TEE in accordance withembodiments of this specification.

FIG. 4 is a flowchart of an example of a process in accordance withembodiments of this specification.

FIG. 5 depicts examples of modules of an apparatus in accordance withembodiments of this specification.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

This specification describes technologies for processing blockchain databased on smart contract operations executed in a trusted executionenvironment (TEE). These technologies generally involve receiving arequest to execute one or more software instructions in a TEE executingon the blockchain node; determining data associated with one or moreblockchain accounts to execute the one or more software instructionsbased on the request; traversing a global state of a blockchain storedin the TEE to locate the data; and executing the one or more softwareinstructions based on the data.

To provide further context for embodiments of this specification, and asintroduced above, distributed ledger systems (DLSs), which can also bereferred to as consensus networks (e.g., made up of peer-to-peer nodes),and blockchain networks, enable participating entities to securely, andimmutably conduct transactions, and store data. Although the termblockchain is generally associated with particular networks, and/or usecases, blockchain is used herein to generally refer to a DLS withoutreference to any particular use case.

A blockchain is a data structure that stores transactions in a way thatthe transactions are immutable. Thus, transactions recorded on ablockchain are reliable and trustworthy. A blockchain includes one ormore blocks. Each block in the chain is linked to a previous blockimmediately before it in the chain by including a cryptographic hash ofthe previous block. Each block also includes a timestamp, its owncryptographic hash, and one or more transactions. The transactions,which have already been verified by the nodes of the blockchain network,are hashed and encoded into a Merkle tree. A Merkle tree is a datastructure in which data at the leaf nodes of the tree is hashed, and allhashes in each branch of the tree are concatenated at the root of thebranch. This process continues up the tree to the root of the entiretree, which stores a hash that is representative of all data in thetree. A hash purporting to be of a transaction stored in the tree can bequickly verified by determining whether it is consistent with thestructure of the tree.

Whereas a blockchain is a decentralized or at least partiallydecentralized data structure for storing transactions, a blockchainnetwork is a network of computing nodes that manage, update, andmaintain one or more blockchains by broadcasting, verifying andvalidating transactions, etc. As introduced above, a blockchain networkcan be provided as a public blockchain network, a private blockchainnetwork, or a consortium blockchain network. Embodiments of thisspecification are described in further detail herein with reference to aconsortium blockchain network. It is contemplated, however, thatembodiments of this specification can be realized in any appropriatetype of blockchain network.

In general, a consortium blockchain network is private among theparticipating entities. In a consortium blockchain network, theconsensus process is controlled by an authorized set of nodes, which canbe referred to as consensus nodes, one or more consensus nodes beingoperated by a respective entity (e.g., a financial institution,insurance company). For example, a consortium of ten (10) entities(e.g., financial institutions, insurance companies) can operate aconsortium blockchain network, each of which operates at least one nodein the consortium blockchain network.

In some examples, within a consortium blockchain network, a globalblockchain is provided as a blockchain that is replicated across allnodes. That is, all consensus nodes are in perfect state consensus withrespect to the global blockchain. To achieve consensus (e.g., agreementto the addition of a block to a blockchain), a consensus protocol isimplemented within the consortium blockchain network. For example, theconsortium blockchain network can implement a practical Byzantine faulttolerance (PBFT) consensus, described in further detail below.

FIG. 1 is a diagram illustrating an example of an environment 100 thatcan be used to execute embodiments of this specification. In someexamples, the environment 100 enables entities to participate in aconsortium blockchain network 102. The environment 100 includescomputing devices 106, 108, and a network 110. In some examples, thenetwork 110 includes a local area network (LAN), wide area network(WAN), the Internet, or a combination thereof, and connects web sites,user devices (e.g., computing devices), and back-end systems. In someexamples, the network 110 can be accessed over a wired and/or a wirelesscommunications link. In some examples, the network 110 enablescommunication with, and within the consortium blockchain network 102. Ingeneral the network 110 represents one or more communication networks.In some cases, the computing devices 106, 108 can be nodes of a cloudcomputing system (not shown), or each computing device 106, 108 can be aseparate cloud computing system including a number of computersinterconnected by a network and functioning as a distributed processingsystem.

In the depicted example, the computing systems 106, 108 can each includeany appropriate computing system that enables participation as a node inthe consortium blockchain network 102. Examples of computing devicesinclude, without limitation, a server, a desktop computer, a laptopcomputer, a tablet computing device, and a smartphone. In some examples,the computing systems 106, 108 hosts one or more computer-implementedservices for interacting with the consortium blockchain network 102. Forexample, the computing system 106 can host computer-implemented servicesof a first entity (e.g., user A), such as a transaction managementsystem that the first entity uses to manage its transactions with one ormore other entities (e.g., other users). The computing system 108 canhost computer-implemented services of a second entity (e.g., user B),such as a transaction management system that the second entity uses tomanage its transactions with one or more other entities (e.g., otherusers). In the example of FIG. 1, the consortium blockchain network 102is represented as a peer-to-peer network of nodes, and the computingsystems 106, 108 provide nodes of the first entity, and second entityrespectively, which participate in the consortium blockchain network102.

FIG. 2 depicts an example of an architecture 200 in accordance withembodiments of this specification. The architecture 200 includes anentity layer 202, a hosted services layer 204, and a blockchain networklayer 206. In the depicted example, the entity layer 202 includes threeparticipants, Participant A, Participant B, and Participant C, eachparticipant having a respective transaction management system 208.

In the depicted example, the hosted services layer 204 includesinterfaces 210 for each transaction management system 208. In someexamples, a respective transaction management system 208 communicateswith a respective interface 210 over a network (e.g., the network 110 ofFIG. 1) using a protocol (e.g., hypertext transfer protocol secure(HTTPS)). In some examples, each interface 210 provides communicationconnection between a respective transaction management system 208, andthe blockchain network layer 206. More particularly, the interface 210communicate with a blockchain network 212 of the blockchain networklayer 206. In some examples, communication between an interface 210, andthe blockchain network layer 206 is conducted using remote procedurecalls (RPCs). In some examples, the interfaces 210 “host” blockchainnetwork nodes for the respective transaction management systems 208. Forexample, the interfaces 210 provide the application programminginterface (API) for access to blockchain network 212.

As described herein, the blockchain network 212 is provided as apeer-to-peer network including a plurality of nodes 214 that immutablyrecord information in a blockchain 216. Although a single blockchain 216is schematically depicted, multiple copies of the blockchain 216 areprovided, and are maintained across the blockchain network 212. Forexample, each node 214 stores a copy of the blockchain. In someembodiments, the blockchain 216 stores information associated withtransactions that are performed between two or more entitiesparticipating in the consortium blockchain network.

A blockchain (e.g., the blockchain 216 of FIG. 2) is made up of a chainof blocks, each block storing data. Examples of data include transactiondata representative of a transaction between two or more participants.While transactions are used herein by way of non-limiting example, it iscontemplated that any appropriate data can be stored in a blockchain(e.g., documents, images, videos, audio). Examples of a transaction caninclude, without limitation, exchanges of something of value (e.g.,assets, products, services, currency). The transaction data is immutablystored within the blockchain. That is, the transaction data cannot bechanged.

Before storing in a block, the transaction data is hashed. Hashing is aprocess of transforming the transaction data (provided as string data)into a fixed-length hash value (also provided as string data). It is notpossible to un-hash the hash value to obtain the transaction data.Hashing ensures that even a slight change in the transaction dataresults in a completely different hash value. Further, and as notedabove, the hash value is of fixed length. That is, no matter the size ofthe transaction data the length of the hash value is fixed. Hashingincludes processing the transaction data through a hash function togenerate the hash value. An example of a hash function includes, withoutlimitation, the secure hash algorithm (SHA)-256, which outputs 256-bithash values.

Transaction data of multiple transactions are hashed and stored in ablock. For example, hash values of two transactions are provided, andare themselves hashed to provide another hash. This process is repeateduntil, for all transactions to be stored in a block, a single hash valueis provided. This hash value is referred to as a Merkle root hash, andis stored in a header of the block. A change in any of the transactionswill result in change in its hash value, and ultimately, a change in theMerkle root hash.

Blocks are added to the blockchain through a consensus protocol.Multiple nodes within the blockchain network participate in theconsensus protocol, and perform work to have a block added to theblockchain. Such nodes are referred to as consensus nodes. PBFT,introduced above, is used as a non-limiting example of a consensusprotocol. The consensus nodes execute the consensus protocol to addtransactions to the blockchain, and update the overall state of theblockchain network.

In further detail, the consensus node generates a block header, hashesall of the transactions in the block, and combines the hash value inpairs to generate further hash values until a single hash value isprovided for all transactions in the block (the Merkle root hash). Thishash is added to the block header. The consensus node also determinesthe hash value of the most recent block in the blockchain (i.e., thelast block added to the blockchain). The consensus node also adds anonce value, and a timestamp to the block header.

In general, PBFT provides a practical Byzantine state machinereplication that tolerates Byzantine faults (e.g., malfunctioning nodes,malicious nodes). This is achieved in PBFT by assuming that faults willoccur (e.g., assuming the existence of independent node failures, and/ormanipulated messages sent by consensus nodes). In PBFT, the consensusnodes are provided in a sequence that includes a primary consensus node,and backup consensus nodes. The primary consensus node is periodicallychanged, Transactions are added to the blockchain by all consensus nodeswithin the blockchain network reaching an agreement as to the worldstate of the blockchain network. In this process, messages aretransmitted between consensus nodes, and each consensus nodes provesthat a message is received from a specified peer node, and verifies thatthe message was not modified during transmission.

In PBFT, the consensus protocol is provided in multiple phases with allconsensus nodes beginning in the same state. To begin, a client sends arequest to the primary consensus node to invoke a service operation(e.g., execute a transaction within the blockchain network). In responseto receiving the request, the primary consensus node multicasts therequest to the backup consensus nodes. The backup consensus nodesexecute the request, and each sends a reply to the client. The clientwaits until a threshold number of replies are received. In someexamples, the client waits for f+1 replies to be received, where f isthe maximum number of faulty consensus nodes that can be toleratedwithin the blockchain network. The final result is that a sufficientnumber of consensus nodes come to an agreement on the order of therecord that is to be added to the blockchain, and the record is eitheraccepted, or rejected.

In some blockchain networks, cryptography is implemented to maintainprivacy of transactions. For example, if two nodes want to keep atransaction private, such that other nodes in the blockchain networkcannot discern details of the transaction, the nodes can encrypt thetransaction data. An example of cryptography includes, withoutlimitation, symmetric encryption, and asymmetric encryption. Symmetricencryption refers to an encryption process that uses a single key forboth encryption (generating ciphertext from plaintext), and decryption(generating plaintext from ciphertext). In symmetric encryption, thesame key is available to multiple nodes, so each node can en-/de-crypttransaction data.

Asymmetric encryption uses keys pairs that each include a private key,and a public key, the private key being known only to a respective node,and the public key being known to any or all other nodes in theblockchain network. A node can use the public key of another node toencrypt data, and the encrypted data can be decrypted using other node'sprivate key. For example, and referring again to FIG. 2, Participant Acan use Participant B's public key to encrypt data, and send theencrypted data to Participant B. Participant B can use its private keyto decrypt the encrypted data (ciphertext) and extract the original data(plaintext). Messages encrypted with a node's public key can only bedecrypted using the node's private key.

Asymmetric encryption is used to provide digital signatures, whichenables participants in a transaction to confirm other participants inthe transaction, as well as the validity of the transaction. Forexample, a node can digitally sign a message, and another node canconfirm that the message was sent by the node based on the digitalsignature of Participant A. Digital signatures can also be used toensure that messages are not tampered with in transit. For example, andagain referencing FIG. 2, Participant A is to send a message toParticipant B. Participant A generates a hash of the message, and then,using its private key, encrypts the hash to provide a digital signatureas the encrypted hash. Participant A appends the digital signature tothe message, and sends the message with digital signature to ParticipantB. Participant B decrypts the digital signature using the public key ofParticipant A, and extracts the hash. Participant B hashes the messageand compares the hashes. If the hashes are same, Participant B canconfirm that the message was indeed from Participant A, and was nottampered with.

In some embodiments, nodes of the blockchain network, and/or nodes thatcommunicate with the blockchain network can operate using TEEs. At ahigh-level, a TEE is a trusted environment within hardware (one or moreprocessors, memory) that is isolated from the hardware's operatingenvironment (e.g., operating system (OS), basic input/output system(BIOS)). In further detail, a TEE is a separate, secure area of aprocessor that ensures the confidentiality, and integrity of codeexecuting, and data loaded within the main processor. Within aprocessor, the TEE runs in parallel with the OS. At least portions ofso-called trusted applications (TAs) execute within the TEE, and haveaccess to the processor and memory. Through the TEE, the TAs areprotected from other applications running in the main OS. Further, theTEE cryptographically isolates TAs from one another inside the TEE.

An example of a TEE includes Software Guard Extensions (SGX) provided byIntel Corporation of Santa Clara, Calif., United States. Although SGX isdiscussed herein by way of example, it is contemplated that embodimentsof this specification can be realized using any appropriate TEE.

SGX provides a hardware-based TEE. In SGX, the trusted hardware is thedie of the central processing until (CPU), and a portion of physicalmemory is isolated to protect select code and data. The isolatedportions of memory are referred to as enclaves. More particularly, anenclave is provided as an enclave page cache (EPC) in memory and ismapped to an application address space. The memory (e.g., DRAM) includesa preserved random memory (PRM) for SGX. The PRM is a continuous memoryspace in the lowest BIOS level and cannot be accessed by any software.Each EPC is a memory set (e.g., 4 KB) that is allocated by an OS to loadapplication data and code in the PRM. EPC metadata (EPCM) is the entryaddress for respective EPCs and ensures that each EPC can only be sharedby one enclave. That is, a single enclave can use multiple EPCs, whilean EPC is dedicated to a single enclave.

During execution of a TA, the processor operates in a so-called enclavemode when accessing data stored in an enclave. Operation in the enclavemode enforces an extra hardware check to each memory access. In SGX, aTA is compiled to a trusted portion, and an untrusted portion. Thetrusted portion is inaccessible by, for example, OS, BIOS, privilegedsystem code, virtual machine manager (VMM), system management mode(SMM), and the like. In operation, the TA runs and creates an enclavewithin the PRM of the memory. A trusted function executed by the trustedportion within the enclave is called by the untrusted portion, and codeexecuting within the enclave sees the data as plaintext data(unencrypted), and external access to the data is denied.

In some embodiments, a virtual machine operating inside of a TEE canprovide a trusted runtime environment for applications to securelyexecute smart contracts. The virtual machine can receive calls from theapplications outside of the TEE. The calls can invoke TEE interfacefunctions to initiate execution of the smart contracts. During smartcontract execution, the virtual machine can retrieve data fromblockchain accounts based on input parameters of the calls or content ofthe smart contracts. Blockchain account addresses and correspondingaccount states are stored as key-value pairs in a data structure knownas MPT. The MPT corresponds to a world state of the blockchain and isstored in the TEE in plaintext. After smart contract execution, one ormore account states may change, new accounts may be added or removed.Accordingly, the world state of the blockchain can be updated inside theTEE based on hash encoding to reflect the changes to the account states.After the world state is updated, calls can be made from the TEE tostore the updated MPT to a database outside of the TEE. The updated MPToutput from the TEE can be encrypted to hide its structure and the datastored therein. Because the MPT is processed and updated inside the TEEand stored outside of the TEE in an encrypted form, the states,behaviors, and relationships of the blockchain accounts can be hiddenfrom blockchain nodes that are not authorized to access such information(e.g., those without the proper key to decrypt the information).

FIG. 3 is a diagram illustrating an example of a structure 300 of a TEEin communication with a database outside of the TEE in accordance withembodiments of this specification. At a high-level, the structure 300includes a TEE 302 that stores a virtual machine and a world state 308of an MPT, and a database 332 in communications with the TEE 302.

As discussed above, a TA, such as an SGX enabled application, caninclude a trusted component (or enclave component) and an untrustedcomponent (application component). The application component is locatedoutside of the TEE 302 and can access the TEE's 302 TCB through enclaveinterface functions. In some embodiments, these enclave interfacefunctions are an application programming interface (API) used by theapplication component. The application component can use the API to make“ecalls” 306 to invoke a virtual machine 304 in the TEE to execute smartcontracts. The virtual machine can be a software program that executesprogram instructions encoded in a particular programming language or ina binary format such as a bitstream. In some cases, the virtual machinemay provide an abstraction layer between the program instructions andthe underlying hardware of the computing device executing the virtualmachine. Such a configuration can allow for the same programinstructions to be executed in the same way across different computingdevices having different hardware.

In some implementations, the virtual machine can be an Ethereum virtualmachine (EVM) under the context of an Ethereum blockchain. It is to beunderstood that other blockchain networks can use other types of ofvirtual machines. After receiving an ecall 306, the virtual machine 304can identify one or more blockchain accounts related to executing asmart contract specified by the ecall 306. The identification can bebased on one or more input parameters of the ecall 306. For example, anecall 306 can be made by an application component to execute a smartcontract for adding a new transaction between two blockchain accounts tothe blockchain. The virtual machine 305 can identify keys (i.e., accountaddresses) to retrieve account balances from the corresponding accountstates. The virtual machine 304 can then calculate the account balancesbased on the transaction amount of the new transaction, and update theworld state 308 accordingly based on hash encoding. Because data in theTEE 302 are in the format of plaintext, no decryption or encryptionneeds to be performed by the virtual machine 304 to update the worldstate 308.

The world state 308 can also be referred to as a global state of theblockchain network. The global state can include a mapping betweenaccount addresses and the account states of the blockchain. The mappingcan be stored in a data structure known as an MPT. The account addressesand account states can be stored in the MPT as key value pairs (KVPs).

The global state MPT is a hash of the global state at a given point intime. The global state can include a root node used as a secure andunique identifier for the MPT. The global state MPT's root node can becryptographically dependent on data representing the account states.

In the structure 300 depicted in FIG. 3, two accounts with respectiveaccount state 0 310 and account state 1 312 are shown under the worldstate 308. Although only two accounts are depicted in FIG. 3, in someimplementations the blockchain can include large numbers of accounts(i.e., more than two). The accounts can be externally owned accounts andcontract accounts. Externally owned accounts can be controlled byprivate keys and are not associated with any code. Contract accounts canbe controlled by their contract code and have code associated with them.

In some embodiments, the account state can include four components asshown under state 1 312. The four components are nonce 314, balance 316,codeHash 318, and storageRoot 320. If the account is an externally ownedaccount, the nonce 314 can represent the number of transactions sentfrom the account address. The balance 316 can represent the digitalassets owned by the account. The codeHash 318 is the hash of an emptystring. The storageRoot 320 is empty. If the account is a contractaccount, the nonce 314 can represent the number of contracts created bythe account. The balance 316 can represent the digital assets owned bythe account. The codeHash 318 can be the hash of a virtual machine codeassociated with the account. The storageRoot 320 can store a hash of theroot node of an MPT referred to as a storage tree. The storage tree canstore contract data by encoding the hash of the storage contents of theaccount. Since the storage tree also has a data structure of an MPT, itcan include one or more branch nodes and leaf nodes that store contractdata or variables. In the structure 300 depicted in FIG. 3, the storagetree includes a branch node 322 and three leaf nodes that store value1324, value2 326, and value3 328. It is to be understood that the storagetree can include additional branch nodes and leaf nodes.

Based on content of ecalls 306, the account state or storage content ofthe storageRoot 320 can be retrieved by the virtual machine 304 toexecute the smart contracts. The execution results can be used to updatethe world state 308 or the storage tree under the storageRoot 320. Insome embodiments, the world state 308 is stored as an MPT. In suchcases, only leaf nodes of the MPT that contain the data and the nodesgoing up the branch relevant to the leaf nodes need to be updated withthe execution results. Afterwards, the virtual machine 304 can make acall (known as an ocall 330) from within the TEE 302 to store the worldstate 308 in a database 332. In some examples, the database 332 can bedatabases for KVPs, such as RocksDB or LevelDB. In some embodiments, theworld state 308 can be encrypted and stored in a cache first beforecache syncing to databases for KVPs. In some examples, the cache can bean overlay DB 329. The overlay DB 329 can be included in the TCB 302 orcan be visited from the TEE 302 through direct memory access. In someembodiments, the world state 308 is encrypted before exiting the TEE302. As such, the world state 308 stored outside of the TEE 302 cannotbe viewed without obtaining the corresponding decryption key.

By including the world state 308 in the TEE 302, the data retrieval andcontent update of the corresponding MPT can be performed in a trustedenvironment inside the TEE 302. The world state 308 is output from theTEE 302 in an encrypted form after it is updated. As such, the datastructure, account relationships, and account behaviors of the worldstate 302 cannot be detected from outside of the TEE 302 without theappropriate cryptographic key. The data privacy of the blockchainaccounts can be enhanced.

FIG. 4 is a flowchart of an example of a process 400 in accordance withembodiments of this specification. For convenience, the process 400 willbe described as being performed by a system of one or more computers,located in one or more locations, and programmed appropriately inaccordance with this specification. For example, computing systems 106,108 of FIG. 1, appropriately programmed, can perform the process 400.

At 402, a blockchain node receives a request to execute one or moresoftware instructions in an enclave of the blockchain node. The enclaveis a TEE executing on the blockchain node. In some examples, the requestis received through an API associated with the enclave. In someembodiments, the applications outside of the enclave can make ecalls(i.e., the request) to the enclave to execute smart contracts in atrusted computing environment. The API can be used by the applicationsto call in. In some embodiments, the request can include one or moreinput parameters and are made to the enclave interface function of theenclave.

At 404, a virtual machine in a TCB of the enclave of the blockchain nodedetermines data associated with one or more blockchain accounts toexecute the one or more software instructions based on the request. Insome examples, a global state of the blockchain stored in the TCB isupdated during execution of the one or more software instructions toproduce an updated global state. In some examples, the global state isreferred to as a world state. The global state can be stored in the TCBand can include a mapping between addresses and states of a plurality ofblockchain accounts of the blockchain. In some embodiments, the globalstate is stored in the TCB as an MPT. In some embodiments, the pluralityof blockchain accounts include one or more externally owned accounts orcontract accounts. Each of the contract accounts includes a storageroot. In some embodiments, the storage root includes a hash of a rootnode of an MPT. The MPT corresponding to the storage root encodes hashof storage contents of the corresponding contract account.

At 406, the virtual machine traverses a global state of a blockchainstored in the TEE to locate the data. In some embodiments, the updatedglobal state is produced by updating the MPT that encodes the hash ofthe storage contents of the corresponding contract account.

At 408, the blockchain node executes the one or more softwareinstructions based on the data. In some embodiments, the updated globalstate is encrypted before stored to the database outside of the enclave.In some embodiments, the databased can be a RocksDB or LevelDB.

FIG. 5 is a diagram of on example of modules of an apparatus 500 inaccordance with embodiments of this specification. The apparatus 500 canbe an example of an embodiment of a trusted hardware including portionsof the CPU and physical memory. The apparatus 500 can correspond to theembodiments described above, and the apparatus 500 includes thefollowing: a receiving module 502 for receiving a request to execute oneor more software instructions in a trusted execution environment (TEE)executing on the blockchain node; a determination module 504 fordetermining data associated with one or more blockchain accounts toexecute the one or more software instructions based on the request; atraversing module 506 for traversing a global state of a blockchainstored in the TEE to locate the data; and an execution module 508 forexecuting the one or more software instructions based on the data.

Optionally, the request includes one or more input parameters and ismade to an enclave interface function of the enclave.

Optionally, the global state is stored in the TCB as a MPT.

Optionally, the global state includes a mapping between addresses andstates of a plurality of blockchain accounts of the blockchain, and theplurality of blockchain accounts include one or more of externally ownedaccounts or contract accounts, and wherein each of the contractsaccounts includes a storage root.

Optionally, the storage root includes a hash of a root node of an MPT,and wherein the MPT encodes hash of storage contents of thecorresponding contract account.

Optionally, the updated global state is produced by updating the MPTthat encodes the hash of the storage contents of the correspondingcontract account.

Optionally, the storage location separate from the enclave is associatedwith a cache or a database.

The techniques described in this specification produce one or moretechnical effects. For example, embodiments of the subject matter permita blockchain virtual machine running in a trusted environment to receivecalls from applications outside of a TEE to execute smart contracts. Bystoring the world state of the blockchain inside the TEE, the virtualmachine can retrieve blockchain data from within the TEE to reduce datatraffic between trusted and untrusted components. Because data travelingbetween the trusted and untrusted components need to be encrypted ordecrypted, less data traffic through enclave can result in lesscomputational resource consumption and higher data security. Moreover,by including the world state within the TEE, the data retrieval andcontent update of the world state can be performed based on plaintext ina trusted environment. The world state is output to a database outsideof the enclave after it is updated and encrypted, such that the datastructure, account relationships, and account behaviors of the worldstate cannot be revealed from outside of the TEE. The data privacy ofthe blockchain accounts can be enhanced.

The described methodology permits enhancement of various blockchaintransactions and overall transaction/data security. Blockchain usersthat initiate the call to execute smart contracts can be confident thatthe computations are performed in a trusted environment and thecomputational results cannot be altered. The updated world state can beencrypted in batch to hide the data structure and permit higher-levelsecurity of underlying data and transactions, as identifying blockchainaccount behaviors and relationships becomes extremely difficult orimpossible with only cyphertext of the blockchain world state is storedoutside of the TEE.

The described methodology can ensure the efficient usage of computerresources (for example, processing cycles, network bandwidth, and memoryusage), because blockchain data from the world state are stored inplaintext, and retrieved and updated inside of the TEE. At least theseactions can minimize or prevent waste of available computer resourceswith respect to blockchain data encryption and decryption. Instead ofvirtual machines needing to decrypt data for smart contract processing,virtual machine can directly operate on plaintext inside of the enclave.

The system, apparatus, module, or unit illustrated in the previousembodiments can be implemented by using a computer chip or an entity, orcan be implemented by using a product having a certain function. Atypical embodiment device is a computer, and the computer can be apersonal computer, a laptop computer, a cellular phone, a camera phone,a smartphone, a personal digital assistant, a media player, a navigationdevice, an email receiving and sending device, a game console, a tabletcomputer, a wearable device, or any combination of these devices.

For an embodiment process of functions and roles of each module in theapparatus, references can be made to an embodiment process ofcorresponding steps in the previous method. Details are omitted here forsimplicity.

Because an apparatus embodiment basically corresponds to a methodembodiment, for related parts, references can be made to relateddescriptions in the method embodiment. The previously describedapparatus embodiment is merely an example. The modules described asseparate parts may or may not be physically separate, and partsdisplayed as modules may or may not be physical modules, may be locatedin one position, or may be distributed on a number of network modules.Some or all of the modules can be selected based on actual demands toachieve the objectives of the solutions of the specification. A personof ordinary skill in the art can understand and implement theembodiments of the present application without creative efforts.

Described embodiments of the subject matter can include one or morefeatures, alone or in combination.

For example, in a first embodiment, receiving, by a blockchain node, arequest to execute one or more software instructions in a trustedexecution environment (TEE) executing on the blockchain node;determining, by a virtual machine in the TEE, data associated with oneor more blockchain accounts to execute the one or more softwareinstructions based on the request; traversing, by the virtual machine, aglobal state of a blockchain stored in the TEE to locate the data; andexecuting, by the virtual machine, the one or more software instructionsbased on the data.

The foregoing and other described embodiments can each, optionally,include one or more of the following features:

A first feature, combinable with any of the following features,specifies that the request includes one or more input parameters and ismade to an interface function of the TEE.

A second feature, combinable with any of the previous or followingfeatures, specifies that wherein the global state is stored in the TEEas a Merkle Patricia tree (MPT).

A third feature, combinable with any of the previous or followingfeatures, specifies that wherein the global state includes a mappingbetween addresses and states of a plurality of blockchain accounts ofthe blockchain, and the plurality of blockchain accounts include one ormore of externally owned accounts or contract accounts, and wherein eachof the contracts accounts includes a storage root.

A fourth feature, combinable with any of the previous or followingfeatures, specifies that the storage root includes a hash of a root nodeof an MPT, and wherein the MPT encodes hash of storage contents of thecorresponding contract account.

A fifth feature, combinable with any of the previous or followingfeatures, specifies that the updated global state is produced byupdating the MPT that encodes the hash of the storage contents of thecorresponding contract account.

A sixth feature, combinable with any of the previous or followingfeatures, specifies that the storage location separate from the TEE isassociated with a cache or a database.

A seventh feature, combinable with any of the previous or followingfeatures, specifies that the request is received through an applicationprogramming interface associated with the TEE.

A eighth feature, combinable with any of the previous or followingfeatures, specifies that the global state of a blockchain stored in theTEE is updated during execution of the one or more software instructionsto produce an updated global state, and the computer-implemented methodfurther comprises: in response to executing the one or more softwareinstructions, generating, by the blockchain node, an encryptedrepresentation of the updated global state; and storing, by theblockchain node, the encrypted representation of the updated globalstate in a storage location separate from the TEE

Embodiments of the subject matter and the actions and operationsdescribed in this specification can be implemented in digital electroniccircuitry, in tangibly-embodied computer software or firmware, incomputer hardware, including the structures disclosed in thisspecification and their structural equivalents, or in combinations ofone or more of them. Embodiments of the subject matter described in thisspecification can be implemented as one or more computer programs, e.g.,one or more modules of computer program instructions, encoded on acomputer program carrier, for execution by, or to control the operationof, data processing apparatus. For example, a computer program carriercan include one or more computer-readable storage media that haveinstructions encoded or stored thereon. The carrier may be a tangiblenon-transitory computer-readable medium, such as a magnetic, magnetooptical, or optical disk, a solid state drive, a random access memory(RAM), a read-only memory (ROM), or other types of media. Alternatively,or in addition, the carrier may be an artificially generated propagatedsignal, e.g., a machine-generated electrical, optical, orelectromagnetic signal that is generated to encode information fortransmission to suitable receiver apparatus for execution by a dataprocessing apparatus. The computer storage medium can be or be part of amachine-readable storage device, a machine-readable storage substrate, arandom or serial access memory device, or a combination of one or moreof them. A computer storage medium is not a propagated signal.

A computer program, which may also be referred to or described as aprogram, software, a software application, an app, a module, a softwaremodule, an engine, a script, or code, can be written in any form ofprogramming language, including compiled or interpreted languages, ordeclarative or procedural languages; and it can be deployed in any form,including as a stand-alone program or as a module, component, engine,subroutine, or other unit suitable for executing in a computingenvironment, which environment may include one or more computersinterconnected by a data communication network in one or more locations.

A computer program may, but need not, correspond to a file in a filesystem. A computer program can be stored in a portion of a file thatholds other programs or data, e.g., one or more scripts stored in amarkup language document, in a single file dedicated to the program inquestion, or in multiple coordinated files, e.g., files that store oneor more modules, sub programs, or portions of code.

Processors for execution of a computer program include, by way ofexample, both general- and special-purpose microprocessors, and any oneor more processors of any kind of digital computer. Generally, aprocessor will receive the instructions of the computer program forexecution as well as data from a non-transitory computer-readable mediumcoupled to the processor.

The term “data processing apparatus” encompasses all kinds ofapparatuses, devices, and machines for processing data, including by wayof example a programmable processor, a computer, or multiple processorsor computers. Data processing apparatus can include special-purposelogic circuitry, e.g., an FPGA (field programmable gate array), an ASIC(application specific integrated circuit), or a GPU (graphics processingunit). The apparatus can also include, in addition to hardware, codethat creates an execution environment for computer programs, e.g., codethat constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, or a combination of one or moreof them.

The processes and logic flows described in this specification can beperformed by one or more computers or processors executing one or morecomputer programs to perform operations by operating on input data andgenerating output. The processes and logic flows can also be performedby special-purpose logic circuitry, e.g., an FPGA, an ASIC, or a GPU, orby a combination of special-purpose logic circuitry and one or moreprogrammed computers.

Computers suitable for the execution of a computer program can be basedon general or special-purpose microprocessors or both, or any other kindof central processing unit. Generally, a central processing unit willreceive instructions and data from a read only memory or a random accessmemory or both. Elements of a computer can include a central processingunit for executing instructions and one or more memory devices forstoring instructions and data. The central processing unit and thememory can be supplemented by, or incorporated in, special-purpose logiccircuitry.

Generally, a computer will also include, or be operatively coupled toreceive data from or transfer data to one or more storage devices. Thestorage devices can be, for example, magnetic, magneto optical, oroptical disks, solid state drives, or any other type of non-transitory,computer-readable media. However, a computer need not have such devices.Thus, a computer may be coupled to one or more storage devices, such as,one or more memories, that are local and/or remote. For example, acomputer can include one or more local memories that are integralcomponents of the computer, or the computer can be coupled to one ormore remote memories that are in a cloud network. Moreover, a computercan be embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storagedevice, e.g., a universal serial bus (USB) flash drive, to name just afew.

Components can be “coupled to” each other by being commutatively such aselectrically or optically connected to one another, either directly orvia one or more intermediate components. Components can also be “coupledto” each other if one of the components is integrated into the other.For example, a storage component that is integrated into a processor(e.g., an L2 cache component) is “coupled to” the processor.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on, orconfigured to communicate with, a computer having a display device,e.g., a LCD (liquid crystal display) monitor, for displaying informationto the user, and an input device by which the user can provide input tothe computer, e.g., a keyboard and a pointing device, e.g., a mouse, atrackball or touchpad. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback, e.g., visual feedback,auditory feedback, or tactile feedback; and input from the user can bereceived in any form, including acoustic, speech, or tactile input. Inaddition, a computer can interact with a user by sending documents toand receiving documents from a device that is used by the user; forexample, by sending web pages to a web browser on a user's device inresponse to requests received from the web browser, or by interactingwith an app running on a user device, e.g., a smartphone or electronictablet. Also, a computer can interact with a user by sending textmessages or other forms of message to a personal device, e.g., asmartphone that is running a messaging application, and receivingresponsive messages from the user in return.

This specification uses the term “configured to” in connection withsystems, apparatus, and computer program components. For a system of oneor more computers to be configured to perform particular operations oractions means that the system has installed on it software, firmware,hardware, or a combination of them that in operation cause the system toperform the operations or actions. For one or more computer programs tobe configured to perform particular operations or actions means that theone or more programs include instructions that, when executed by dataprocessing apparatus, cause the apparatus to perform the operations oractions. For special-purpose logic circuitry to be configured to performparticular operations or actions means that the circuitry has electroniclogic that performs the operations or actions.

While this specification contains many specific embodiment details,these should not be construed as limitations on the scope of what isbeing claimed, which is defined by the claims themselves, but rather asdescriptions of features that may be specific to particular embodiments.Certain features that are described in this specification in the contextof separate embodiments can also be realized in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiments can also be realized in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially be claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claim may be directed to a subcombination orvariation of a subcombination.

Similarly, while operations are depicted in the drawings and recited inthe claims in a particular order, this should not be understood asrequiring that such operations be performed in the particular ordershown or in sequential order, or that all illustrated operations beperformed, to achieve desirable results. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system modules and components in the embodimentsdescribed above should not be understood as requiring such separation inall embodiments, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products.

Particular embodiments of the subject matter have been described. Otherembodiments are within the scope of the following claims. For example,the actions recited in the claims can be performed in a different orderand still achieve desirable results. As one example, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In some cases, multitasking and parallel processing may beadvantageous.

What is claimed is:
 1. A computer-implemented method for processingblockchain data under a trusted execution environment (TEE), the methodcomprising: receiving, by a blockchain node, a request to execute one ormore software instructions in the TEE executing on the blockchain node;determining, by a virtual machine in the TEE based on the request, dataassociated with one or more blockchain accounts related to the executionof the one or more software instructions; traversing, by the virtualmachine, a global state of a blockchain stored in the TEE to locate thedata associated with the one or more blockchain accounts; generating, bythe virtual machine, an updated global state by encoding a hash of astorage content of the one or more blockchain accounts; in response toexecuting the one or more software instructions, generating, by theblockchain node, an encrypted representation of the updated globalstate; and storing, by the blockchain node, the encrypted representationof the updated global state in a cache separate from the TEE for cachesyncing the encrypted representation of the updated global state to adatabase of a trusted computing base that is separate from the TEE. 2.The computer-implemented method of claim 1, wherein the encryptedrepresentation of the updated global state is generated using a privatekey of the blockchain node.
 3. The computer-implemented method of claim1, wherein the request includes one or more input parameters and is madeto an interface function of the TEE.
 4. The computer-implemented methodof claim 1, wherein the global state is stored in the TEE as a MerklePatricia tree (MPT).
 5. The computer-implemented method of claim 1,wherein the global state includes a mapping between addresses and statesof the one or more blockchain accounts of the blockchain, and the one ormore blockchain accounts include one or more of externally ownedaccounts or contract accounts, and wherein each of the contractsaccounts includes a storage root.
 6. The computer-implemented method ofclaim 5, wherein the storage root includes a root node hash of a MerklePatricia tree (MPT), and wherein the MPT encodes a hash of storagecontent of a corresponding contract account.
 7. The computer-implementedmethod of claim 6, wherein the updated global state is produced byupdating the MPT that encodes the hash of the storage content of thecorresponding contract account.
 8. The computer-implemented method ofclaim 1, wherein the cache comprises an overlay database accessible fromthe TEE through direct memory access.
 9. The computer-implemented methodof claim 1, wherein the request is received through an applicationprogramming interface associated with the TEE.
 10. A non-transitory,computer-readable storage medium storing one or more instructionsexecutable by a computer system to perform operations for processingblockchain data under a trusted execution environment (TEE), theoperations comprising: receiving, by a blockchain node, a request toexecute one or more software instructions in the TEE executing on theblockchain node; determining, by a virtual machine in the TEE based onthe request, data associated with one or more blockchain accountsrelated to the execution of the one or more software instructions;traversing, by the virtual machine, a global state of a blockchainstored in the TEE to locate the data associated with the one or moreblockchain accounts; generating, by the virtual machine, an updatedglobal state by encoding a hash of a storage content of the one or moreblockchain accounts; in response to executing the one or more softwareinstructions, generating, by the blockchain node, an encryptedrepresentation of the updated global state; and storing, by theblockchain node, the encrypted representation of the updated globalstate in a cache separate from the TEE for cache syncing the encryptedrepresentation of the updated global state to a database of a trustedcomputing base that is separate from the TEE.
 11. The non-transitory,computer-readable storage medium of claim 10, wherein the encryptedrepresentation of the updated global state is generated using a privatekey of the blockchain node.
 12. The non-transitory, computer-readablestorage medium of claim 10, wherein the request includes one or moreinput parameters and is made to an interface function of the TEE. 13.The non-transitory, computer-readable storage medium of claim 10,wherein the global state is stored in the TEE as a Merkle Patricia tree(MPT).
 14. The non-transitory, computer-readable storage medium of claim10, wherein the global state includes a mapping between addresses andstates of the one or more blockchain accounts of the blockchain, and theone or more blockchain accounts include one or more of externally ownedaccounts or contract accounts, and wherein each of the contractsaccounts includes a storage root.
 15. The non-transitory,computer-readable storage medium of claim 14, wherein the storage rootincludes a root node hash of a Merkle Patricia tree (MPT), and whereinthe MPT encodes a hash of storage content of a corresponding contractaccount.
 16. The non-transitory, computer-readable storage medium ofclaim 15, wherein the updated global state is produced by updating theMPT that encodes the hash of the storage content of the correspondingcontract account.
 17. The non-transitory, computer-readable storagemedium of claim 10, wherein the cache comprises an overlay databaseaccessible from the TEE through direct memory access.
 18. Thenon-transitory, computer-readable storage medium of claim 10, whereinthe request is received through an application programming interfaceassociated with the TEE.
 19. A computer-implemented system, comprising:one or more computers; and one or more computer memory devicesinteroperably coupled with the one or more computers and havingtangible, non-transitory, machine-readable media storing one or moreinstructions that, when executed by the one or more computers, performone or more operations for processing blockchain data under a trustedexecution environment (TEE), the operations comprising: receiving, by ablockchain node, a request to execute one or more software instructionsin the TEE executing on the blockchain node, determining, by a virtualmachine in the TEE based on the request, data associated with one ormore blockchain accounts related to the execution of the one or moresoftware instructions, traversing, by the virtual machine, a globalstate of a blockchain stored in the TEE to locate the data associatedwith the one or more blockchain accounts, generating, by the virtualmachine, an updated global state by encoding a hash of a storage contentof the one or more blockchain accounts, in response to executing the oneor more software instructions, generating, by the blockchain node, anencrypted representation of the updated global state, and storing, bythe blockchain node, the encrypted representation of the updated globalstate in a cache separate from the TEE for cache syncing the encryptedrepresentation of the updated global state to a database of a trustedcomputing base that is separate from the TEE.
 20. The system of claim19, wherein the encrypted representation of the updated global state isgenerated using a private key of the blockchain node.
 21. The system ofclaim 19, wherein the request includes one or more input parameters andis made to an interface function of the TEE.
 22. The system of claim 19,wherein the global state is stored in the TEE as a Merkle Patricia tree(MPT).
 23. The system of claim 19, wherein the global state includes amapping between addresses and states of the one or more blockchainaccounts of the blockchain, and the one or more blockchain accountsinclude one or more of externally owned accounts or contract accounts,and wherein each of the contracts accounts includes a storage root. 24.The system of claim 23, wherein the storage root includes a root nodehash of a Merkle Patricia tree (MPT), and wherein the MPT encodes a hashof storage content of a corresponding contract account.
 25. The systemof claim 24, wherein the updated global state is produced by updatingthe MPT that encodes the hash of the storage content of thecorresponding contract account.
 26. The system of claim 19, wherein thecache comprises an overlay database accessible from the TEE throughdirect memory access.
 27. The system of claim 19, wherein the request isreceived through an application programming interface associated withthe TEE.